Optimizing timeouts
You can extend the timeout settings on an appserver to optimize it for testing and demo usage. Extending timeouts prevents problems that come from letting iMIS (Desktop or web) sit idle for long periods of time.
Caution! Do not set excessive timeouts (especially the session timeout) on production sites: idle sessions sitting for long periods of time can exhaust the server's memory.
To extend timeouts
1. In IIS Manager, expand the Application Pools node, right-click the Default AppPool and select Properties. (This refers to IIS6; see Optimizing timeouts on production appservers for IIS7.)
□ Performance tab, under "Idle timeout": increase the value.
□ Recycling tab, the first option: increase the value.
2. Open the web.config file for each iMIS site:
□ Find the following setting and change the timeout value to any number of minutes up to the maximum 2147483647 (4085 years):
<sessionState mode="InProc" stateConnectionString="tcpip=127.0.0.1:42424" sqlConnectionString="data source=127.0.0.1;user id=sa;password=" cookieless="false" timeout="20" />
□ To extend the idle “authentication ticket” timeout for non-Remember Me logins (which never time out), change the following value to any number of minutes up to the maximum 2147483647 (4085 years):
<add key="Authenticate.PersistLogin.Minutes" value="0" />
Enabling concurrent Casual and Full access
If your staff users need to run both administrative and staff views on the same workstation concurrently, then you need to create a separate Casual site (virtual directory) for them.
To enable Casual and Full access at the same time, you must separate the authentication cookies. This lets you open administrative and staff clients simultaneously for different license levels, without logins colliding.
To separate authentication cookies
1. Create separate virtual directories for each view.
□ Copy the \ASI\iMIS\net folder to another location (such as ASI\iMIS\net2)
□ In IIS Admin, create a new virtual directory (such as iMISCasual) and point it at the new folder.
2. Configure the sites to use different authentication cookie names.
□ In each web.config file, locate the following section:
<authentication mode="Forms">
<forms name="Login" loginUrl="~/AsiCommon/Controls/Shared/FormsAuthentication/Login.aspx" />
</authentication>
□ Change the name attribute's value to be unique (such as LoginFull, LoginCasual, and LoginPublic) for each site, then save and close the files.
□ Point your administrative view at one site (such as iMIS) and your browser at the other (such as iMISCasual), as needed.